Pull request overview

This PR fixes issue #140, where GetImplementingProperty throws System.InvalidOperationException ("Sequence contains no matching element") when a class has both a public property and an explicit interface implementation property sharing the same name (e.g., int Id { get; set; } and string IStringId.Id => ...). The fix changes First(...) to FirstOrDefault(...) ?? propertyInfo in TypeExtensions.GetImplementingProperty, so that when the matching property cannot be found in the derived type's properties, the code gracefully falls back to returning the original interface property rather than throwing.

Changes:

• The single-line source fix in TypeExtensions.GetImplementingProperty replaces First with FirstOrDefault and adds a ?? propertyInfo fallback to prevent the crash.
• New unit tests and helper types added to TypeExtensionTests.cs verifying both GetImplementingProperty and GetConcreteProperty return the concrete explicit interface implementation (not the interface property) and do not throw.
• New functional and generator snapshot tests added to validate end-to-end behavior for the explicit interface implementation scenario.

Reviewed changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 2 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.